⚠️ 🔍 Microsoft Defender XDR (XdrLogRaider)

⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID [parameters('connectorDefinitionName')]
Publisher Alex Kefallonitis
Used in Solutions XdrLogRaider
Collection Method CCF
Connector Definition Files azuredeploy_XdrLogRaider_FunctionApp.json
Ingestion API Log Ingestion API — Sibling ARM template declares DCR / Log Ingestion API resources
Microsoft Learn View on Learn

Open-source Microsoft Sentinel data connector for Microsoft Defender XDR portal-internal /apiproxy/* audit and reporting endpoints. Self-hosted in your Azure subscription with cookie-based authentication and transparent SSO refresh. Read-only by design — no action verbs are ever invoked on the Defender portal.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
Defender_AnalyticsData_CL ? ✓ ?
Defender_AttackSimulation_CL ? ✓ ?
Defender_CloudApps_CL ? ✓ ?
Defender_Configuration_CL ? ✓ ?
Defender_EndpointManagement_CL ? ✓ ?
Defender_ExposureManagement_CL ? ✓ ?
Defender_Identity_CL ? ✓ ?
Defender_Operations_CL ? ✓ ?
Defender_PortalServices_CL ? ✓ ?
Defender_SecureScore_CL ? ✓ ?
Defender_VulnerabilityManagement_CL ? ✓ ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

1. Step 1 · Service account credentials (automatic)

The deployment template stored your service account credentials (password and TOTP seed or Passkey PEM) into the deployment Key Vault. No manual action is required if the deployment completed successfully.

2. Step 2 · Unattended authentication (automatic)

On the first cycle, the Function App performs an unattended Entra OAuth login using the stored credentials. Single sign-on state is captured and persisted so subsequent cycles use silent refresh. No operator interaction is required.

3. Step 3 · Verify ingestion (~10 minutes after deploy)

Query the workspace for ingested rows in any active Defender_<Category>_CL table. Cycle telemetry (Boot, Auth, Cycle, Entry events) is available via Application Insights for end-to-end observability.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index